All features supporting the SysML v2 BETA specification are currently ALPHA and subject to change. The final SysML 2.0.0 specification is expected to be officially adopted in the second half of 2025. While there have been many questions during the finalization, we believe this implementation provides enough value for early adopters to start preparing to create and execute models using the new specification. We will be expanding support for the specification through finalization, into SysML v2.1, and beyond. There are a small number of remaining issues related to execution scheduled for revision in SysMLv2.1. We will be expanding and clarifying support for SysML v2.x throughout the upcoming language revision process. Consult the What's New and Modeling with SysML v2 pages for more information about what is currently supported.

SysML v2 Execution

To better understand how Behavior Execution Engine interprets and executes your SysML v2 model, refer to the following pages:

Section	Description
Execution Heuristics	This page details the rules of thumb for building SysML v2 models that Behavior Execution Engine can successfully simulate. Behavior Execution Engine currently supports executing models with all the following SysML v2 offerings. If an offering is not listed below, Behavior Execution Engine may not support its intended functionality as specified. Actions Successions States Transitions Flows Items and Parts Units
Simulation Events	States are inherently event oriented since transitions depend on events to determine when to proceed from one state to another. When executing states, Behavior Execution Engine checks which transitions have triggers observing events that determine the time when a source state might exit. This allows Behavior Execution Engine to advance simulation time forward precisely from event to event instead of having to advance the simulation in explicit time steps. This means you can model behavior without having to worry about inaccuracies introduced by numerical computation. In particular, using precise moments in continuous time allows for more natural and accurate use of change triggers. Behavior Execution Engine also enables you to delegate the detection of threshold satisfaction intervals to analysis tools like the Ansys Systems Tool Kit^® (STK^®) application. This means you can let the analysis tools handle event detection based on the broader environment or context of your system (e.g., gravity, relative location, etc.) while you focus on modeling the behavior of your system.

Section

Description

Execution Heuristics

This page details the rules of thumb for building SysML v2 models that Behavior Execution Engine can successfully simulate. Behavior Execution Engine currently supports executing models with all the following SysML v2 offerings. If an offering is not listed below, Behavior Execution Engine may not support its intended functionality as specified.

Simulation Events

States are inherently event oriented since transitions depend on events to determine when to proceed from one state to another. When executing states, Behavior Execution Engine checks which transitions have triggers observing events that determine the time when a source state might exit. This allows Behavior Execution Engine to advance simulation time forward precisely from event to event instead of having to advance the simulation in explicit time steps. This means you can model behavior without having to worry about inaccuracies introduced by numerical computation. In particular, using precise moments in continuous time allows for more natural and accurate use of change triggers. Behavior Execution Engine also enables you to delegate the detection of threshold satisfaction intervals to analysis tools like the Ansys Systems Tool Kit^® (STK^®) application. This means you can let the analysis tools handle event detection based on the broader environment or context of your system (e.g., gravity, relative location, etc.) while you focus on modeling the behavior of your system.